Secure system

ABSTRACT

A device may receive application questions for an individual applying for credit with an organization. The device may broadcast the application questions to additional devices that have access to a distributed ledger for sharing credit worthiness information to cause at least one of the additional devices to generate an application response to the application questions and to process the application response using a smart contract. The device may receive one or more application responses that have been encrypted. Each of the application responses may include particular credit worthiness information relating to the individual. The device may decrypt the application responses. The device may determine a credit worthiness score for the individual using the application responses. The device may perform one or more actions that allow the device or another device associated with the organization to use the credit worthiness score to determine whether to approve the individual for credit.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/506,304, filed Jul. 9, 2019 (now U.S. Pat. No. 11,030,686), which isa continuation of U.S. patent application Ser. No. 15/983,617, filed May18, 2018 (now U.S. Pat. No. 10,380,685), which are incorporated hereinby reference in their entireties.

BACKGROUND

A blockchain is a distributed database that maintains acontinuously-growing list of records, called blocks, that may be linkedtogether to form a chain. Each block in the blockchain may contain atimestamp and a link to a previous block and/or transaction. The blocksmay be secured from tampering and revision. In addition, a blockchainmay include a secure transaction ledger database shared by partiesparticipating in an established, distributed network of computers. Ablockchain may record a transaction (e.g., an exchange or transfer ofinformation) that occurs in the network, thereby reducing or eliminatingthe need for trusted/centralized third parties. In some cases, theparties participating in a transaction may not know the identities ofany other parties participating in the transaction but may securelyexchange information. Further, the distributed ledger may correspond toa record of consensus with a cryptographic audit trail that ismaintained and validated by a set of independent computers.

SUMMARY

According to some implementations, a device may include one or morememories and one or more processors that are communicatively coupled tothe one or more memories. The one or more processors may receive, from afirst device, a request for a credit worthiness score for an individualthat is applying for credit. The first device may be associated with anorganization offering the credit. The request may include applicationquestions that have been encrypted using a private key associated with adigital signature of the individual. The first device may be part of anetwork of devices that have access to a distributed ledger for sharingcredit worthiness information of a group of individuals. The one or moreprocessors may broadcast the application questions that have beenencrypted to one or more additional devices to cause at least one of theone or more additional devices to: generate an application response thatincludes responses to the application questions, record the applicationresponse in the distributed ledger, and provide the application responseto the device. The one or more additional devices may be part of thenetwork of devices that have access to the distributed ledger. The oneor more processors may receive, from at least one of the one or moreadditional devices, one or more application responses that have beenencrypted. Each application response, of the one or more applicationresponses, may include particular credit worthiness information relatingto the individual. The one or more processors may decrypt the one ormore application responses. The one or more processors may determine thecredit worthiness score using the one or more application responses thathave been decrypted. The one or more processors may provide the creditworthiness score to the first device to allow the first device to usethe credit worthiness score to determine whether to approve theindividual for the credit.

According to some implementations, a method may include receiving, by adevice, application questions for an individual that is applying forcredit with a first organization. The device may be part of a network ofdevices that have access to a distributed ledger for sharing creditworthiness information for a group of individuals. The applicationquestions may have been encrypted using a private key associated withthe individual. The method may include broadcasting, by the device, theapplication questions to one or more additional devices that have accessto the distributed ledger to cause at least one of the one or moreadditional devices to: generate an application response that includesresponses to the application questions, process the application responseusing a smart contract, and provide the application response to thedevice. The method may include receiving, by the device and from atleast one of the one or more additional devices, one or more applicationresponses that have been encrypted. Each application response, of theone or more application responses, may include particular creditworthiness information relating to the individual. The method mayinclude decrypting, by the device, the one or more applicationresponses. The method may include determining, by the device, a creditworthiness score for the individual using the one or more applicationresponses. The method may include performing, by the device, one or moreactions that allow the device or another device associated with thefirst organization to use the credit worthiness score to determinewhether to approve the individual for credit.

According to some implementations, a non-transitory computer-readablemedium may store instructions that, when executed by one or moreprocessors, cause the one or more processors to receive, from a firstdevice, a request for a credit worthiness score for an individual thatis applying for credit in a first country. The first device may beassociated with an organization offering the credit. The request mayinclude application questions that have been encrypted. The first devicemay be part of a network of devices that have access to a distributedledger for sharing credit worthiness information of a group ofindividuals. The one or more instructions may cause the one or moreprocessors to select one or more additional devices in the network ofdevices as targets to receive the application questions. The one or moreinstructions may cause the one or more processors to broadcast theapplication questions to the one or more additional devices that havebeen selected to permit at least one of the one or more additionaldevices to: generate an application response that includes responses tothe application questions, and provide the application response. The oneor more instructions may cause the one or more processors to receive,from at least one of the one or more additional devices, one or moreapplication responses that have been encrypted. Each applicationresponse, of the one or more application responses, may includeparticular credit worthiness information relating to transactionsperformed by the individual in a second country. The one or moreinstructions may cause the one or more processors to decrypt the one ormore application responses. The one or more instructions may cause theone or more processors to determine the credit worthiness score usingthe one or more application responses that have been decrypted. The oneor more instructions may cause the one or more processors to provide thecredit worthiness score to the first device to allow the first device touse the credit worthiness score to determine whether to approve theindividual for the credit.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1J are diagrams of an example implementation described herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2 .

FIGS. 4-6 are flow charts of an example process for using a securedistributed ledger to manage sharing of credit worthiness information ofindividuals.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

When an individual moves from a first country to a second country, theindividual's credit history from the first country may not be recognizedby lending organizations within the second country. When the individualapplies for credit in the second country (e.g., by applying for a loan,a credit card, etc.), a lender organization (e.g., a bank, a financialinstitution, etc.) may have a difficult time determining whether toprovide the individual with the credit, how much credit to approve,and/or the like.

Additionally, the lending organization may pay a fee to one or morethird party agencies in an effort to obtain the credit information ofthe individual. However, an international exchange of the individual'scredit information between the lender organization and one or more thirdparty agencies raises security concerns and data privacy concerns. Forexample, sharing of credit information of the individual raises securityconcerns due to the risk of the credit information being intercepted byunauthorized parties. Furthermore, different countries have differentdata privacy laws, which may make it difficult for the lendingorganization to interact with the one or more third party agencies in amanner that is compliant with data privacy laws.

Some implementations described herein provide a ledger managementplatform to determine a credit worthiness score of an individual that isapplying for credit in a first country by interacting with a securedistributed ledger to obtain and analyze credit worthiness informationassociated with transactions made by the individual in a second country.For example, the ledger management platform may be part of a network ofdevices that have access to a distributed ledger for sharing creditworthiness information of a group of individuals. In this case, anindividual may move to a first country, and may submit an applicationfor credit with a first organization. After the individual submits theapplication for the credit, a first device associated with the firstorganization may provide, to the ledger management platform, a requestfor a credit worthiness score of the individual. The request may includeapplication questions that may be used to determine the creditworthiness score, and may be encrypted using a private key associatedwith a digital signature of the individual.

Additionally, the ledger management platform may broadcast the encryptedapplication questions to one or more additional devices that have accessto the distributed ledger. This may cause at least one of the one ormore additional devices to generate application responses to theapplication questions, and to provide the application responses to theledger management platform. Furthermore, the ledger management platformmay decrypt the application responses, and may use the applicationresponses to determine the credit worthiness score. Moreover, the ledgermanagement platform may provide the credit worthiness score to the firstdevice to allow the first device to use the credit worthiness score todetermine whether to approve the individual for the credit. During thisprocess, the ledger management platform, the first device, and/or theone or more additional devices may use the distributed ledger to storerecords of exchanges of credit worthiness information that were providedvia the network.

In this way, the ledger management platform is able to provide the firstdevice with a credit worthiness score that may be used to determinewhether to approve the individual for the credit. Additionally, theledger management platform is able to facilitate the distribution ofcredit worthiness information in a manner that is flexible, secure,distributed, and automated. For example, flexibility is provided byenabling execution of various smart contracts to ensure that creditworthiness information is shared in a manner that is compliant with lawsof different jurisdictions.

Additionally, security is provided by supporting the distributed ledgerwith a tamper-resistant data structure (e.g., a blockchain), byimplementing various forms of authentication, by restricting access tothe distributed ledger to particular parties, and/or the like. Forexample, the distributed ledger may improve security by preserving animmutable record of credit worthiness information, by usingcryptographic links between blocks of the distributed ledger (e.g.,reducing the potential for unauthorized tampering with the creditworthiness information), and/or the like. Security is further improvedas a result of devices that have access to the distributed ledgerindependently verifying each transaction that is added to thedistributed ledger. Moreover, use of a distributed ledger also providesfailover protection, in that the ledger management platform may continueto operate in a situation where one or more devices that have access tothe distributed ledger fail.

Furthermore, several different stages of the process for managing creditworthiness information are automated, which may remove humansubjectivity and waste from the process, and which may improve speed andefficiency of the process and conserve computing resources (e.g.,processor resources, memory resources, and/or the like). Additionally,implementations described herein use a rigorous, computerized process toperform tasks or roles that were not previously performed or werepreviously performed using subjective human intuition or input. Finally,automating the process for managing credit worthiness informationconserves computing resources (e.g., processor resources, memoryresources, and/or the like) that would otherwise be wasted by usingmultiple different types of devices with different software, protocols,and configurations, and computing resources that would otherwise bewasted correcting problems that would arise from lack of consistency inthe application of various transactions related to the credit worthinessinformation.

FIGS. 1A-1J are diagrams of an overview of an example implementation 100described herein. For example, example implementation 100 may include anetwork of nodes (e.g., server computers, personal computers, etc.) thathave access to a distributed ledger for sharing credit worthinessinformation of an individual. In this case, the network of nodes mayinclude a management node, such as a ledger management platform, that isable to orchestrate distribution of information to other nodes in thenetwork and/or is able to determine a credit worthiness score for theindividual, as described herein.

As shown in FIG. 1A, and by reference number 102, a group oforganizations (e.g., banks, financial institutions, lenderorganizations, etc.) may sign up for access to the distributed ledger,which may be used for sharing credit worthiness information of a groupof individuals. The credit worthiness information may be for a group ofindividuals that are customers of the group of organizations, such asindividuals that have a credit score, individuals that have performedtransactions that may be used to determine a credit score, and/or thelike.

Additionally, the credit worthiness information may include creditinformation relating to transactions made between individuals and afirst group of organizations and/or rating information relating totransactions between individuals and a second group of organizations.The credit information may include information indicating a creditscore, an income, a number of open lines of credit, an amount ofoutstanding debt, a mortgage payment history, a number timely (oruntimely) payments made on behalf of the individuals, and/or the like.The rating information may include one or more third-party ratings thatthe particular individual has accrued via transactions with the secondgroup of organizations, such as a ride sharing rating, a ratingassociated with online purchases, and/or the like.

In some implementations, employees of each organization may interactwith an interface to sign up for access to the distributed ledger. Forexample, employees may use devices associated with the group oforganizations (shown as a Device of Organization 1, a Device ofOrganization 2, and a Device of Organization N) to access an interface(e.g., a web interface, an application interface, etc.) that permitsorganizations to sign up for access to the distributed ledger.

As an example, an employee of a first organization may sign up foraccess to the distributed ledger by interacting with a web interfacedisplayed on a first device (e.g., the Device of Organization 1) tocreate a profile for the first organization. The profile may includeinformation indicating an organization name, an organization address, aunique identifier associated with the organization (e.g., a taxidentifier), an organization type (e.g., a particular type of financialinstitution), one or more countries in which the first organizationoperates, an approval by a third-party organization that verifies theauthenticity of organizations, and/or any other information that may beneeded to obtain access to the distributed ledger.

In some implementations, the network of nodes that have access to thedistributed ledger may be supported using a number of different types ofdevices or network configurations. For example, the nodes in the networkmay be one or more servers that are hosted within a number of differentdata centers distributed worldwide. In this case, after an organizationcreates a profile, the ledger management platform may assign or dedicateone or more nodes to the organization, and may provide a deviceassociated with the organization with login information needed to accessone or more services provided by the one or more nodes. For example, anorganization may be assigned a first node, and an employee of theorganization may use a device associated with the organization (e.g., alocal desktop computer) to access a web interface that allows theemployee to use one or more services provided by first node (e.g., theemployee might use the first node to request credit worthinessinformation of an individual, as described further herein).

Additionally, or alternatively, the devices associated with the group oforganizations may be used as nodes of the network. In this case, theledger management platform may provide the devices associated with theorganizations with instructions on how to install one or more softwareresources needed to allow the devices associated with the organizationsto serve as the nodes. In some implementations, the network of nodes maybe configured without a management node (e.g., the ledger managementplatform). In this case, one or more of the nodes may support softwareresources (e.g., virtual resources) that allow the one or more nodes toperform one or more functions described as being performed by the ledgermanagement platform.

In this way, the ledger management platform is able to allow a group oforganizations to sign up for access to the distributed ledger.

As shown in FIG. 1B, and by reference number 104, the ledger managementplatform may receive one or more smart contracts. For example, theledger management platform may receive one or more smart contracts fromdevices associated with organizations that have access to thedistributed, third-party organizations, and/or the like. In this case,the one or more smart contracts may be able to digitally facilitate,verify, and/or enforce negotiation or performance of a contract. Thecontract may involve an exchange of credit worthiness information of anindividual and a particular type of payment (e.g., cryptocurrency,etc.).

In some implementations, the one or more smart contracts may includeapplication questions that request credit worthiness information of anindividual. For example, a smart contract may include credit-relatedapplication questions, such as a question requesting an individual'scredit score, a current amount of outstanding debt, an income, amortgage payment history, and/or the like. Additionally, oralternatively, the smart contact may include rating-related applicationquestions, such as a question requesting an individual's rating for apopular ride sharing service, an individual's rating for a portal thatsupports online shopping, and/or the like.

In some implementations, the one or more smart contacts may include oneor more conditions that, if satisfied, cause the ledger managementplatform to orchestrate providing payment to an organization thatprovided the requested credit worthiness information of the individual.For example, a smart contract may request a credit score of anindividual, and may include a condition that is satisfied only if avalue provided as a response is within a range of possible creditscores. As another example, a smart contract may request creditworthiness information using a yes or no question, and may include acondition that is only satisfied if a response is in a yes or no format.As another example, a smart contract may request credit worthinessinformation, and may include a condition that is satisfied only if aresponse is in compliance with data privacy laws of a particularjurisdiction.

As shown as an example, the ledger management platform may receive afirst smart contract (shown as Smart Contract A) and a second smartcontract (shown as Smart Contract B). As shown, the first smart contractand the second smart contract may phrase application questionsdifferently such that the application questions are in compliance withdata privacy laws of a first jurisdiction (shown as Country A) and asecond jurisdiction (shown as Country B).

As shown by reference number 106, the ledger management platform mayprovide the one or more smart contracts to one or more devicesassociated with validation entities. For example, one or more validationentities may be used to independently validate and/or verify thatparticular smart contracts comply with rules or protocols used withinthe distributed ledger, data privacy laws of particular jurisdictions,and/or the like.

In some implementations, the one or more validation entities may beorganizations capable of running a validation node (e.g., a validationnode on an Ethereum platform). Additionally, or alternatively, the oneor more validation entities may be organizations that are not part ofthe distributed ledger. Additionally, or alternatively, the one or morevalidation entities may be law firms, regulatory agencies, and/ororganizations capable of verifying whether the smart contract is incompliance with data privacy laws of particular jurisdictions.

As shown by reference number 108, the devices associated with thevalidation entities may be used to validate the one or more smartcontracts. As shown by reference number 110, the devices associated withthe validation entities may provide the one more validated smartcontracts to the ledger management platform. In some cases, a validationentity may join the network of nodes, and may include, as metadatawithin each smart contract, an authorized signature indicating that thevalidation entity has reviewed the smart contract and that the smartcontract is in compliance with a particular rule or protocol used bydevices with access to the distributed ledger, that the smart contractis in compliance with data privacy laws of a particular jurisdiction,and/or the like.

In some implementations, the ledger management platform may validate asmart contract using a machine learning technique. For example, theledger management platform may train a machine learning model on dataprivacy law information and historical smart contracts that were foundto be in compliance with the laws of the particular jurisdiction, andmay use the machine learning model to verify whether a smart contractcomplies with particular data privacy laws.

The data privacy law information may indicate a restriction associatedwith a type of personal information that may be shared, a restrictionassociated with a degree to which personal information may be shared, arestriction indicating that personal information collected is able to beremoved upon request of the individual, a restriction indicating that anindividual is to be informed as to a specific purpose with which theindividual's personal information may be used, and/or the like. Thehistorical smart contracts may include particular application questionsthat were asked, conditions that were used, indicators of whetherparticular application questions were in compliance with the laws of theparticular jurisdiction, and/or the like.

Additionally, the ledger management platform may use the machinelearning model to determine whether particular application questionscomply with data privacy laws of the particular jurisdiction. Forexample, the ledger management platform may receive a new smart contractthat includes application questions that have yet to be validated. Inthis case, the ledger management platform may provide the newapplication questions as input to the machine learning model to causethe machine learning model to output an indicator of a likelihood ofeach of the new application questions complying with the data privacylaws of a particular jurisdiction. Additionally, the ledger managementplatform may validate an application question if the applicationquestion satisfies a threshold confidence level.

In some implementations, the ledger management platform may receive anexpiring smart contract. For example, because certain data privacy lawsmay restrict a manner in which personal information of individuals maybe distributed over the network of nodes, the ledger management platformmay receive a smart contract that expires after a threshold time period.This may allow nodes requesting and/or receiving personal information tohave limited access to the personal information before the smartcontract expires and the personal information included in the smartcontract is permanently deleted.

In some implementations, the ledger management platform may receive asmart contract that includes specific functions that comply with dataprivacy laws of particular jurisdictions. For example, rather than useseparate smart contacts for each jurisdiction, the ledger managementplatform may receive or be configured with a single smart contract thatincludes separate functions for each jurisdiction, such that eachfunction includes application questions that comply with a particularjurisdiction.

In some implementations, the network of nodes may be configured suchthat multiple distributed ledgers are utilized, where each distributedledger uses a different smart contract. For example, the ledgermanagement platform may be used to manage exchanges of credit worthinessinformation using a group of distributed ledgers, whereby eachdistributed ledger uses a particular smart contract that is incompliance with laws of a particular jurisdiction.

In this way, the ledger management platform is able to receive andvalidate smart contracts. Furthermore, the ledger management platformprovides flexibility by enabling execution of various smart contracts toensure that credit worthiness information is shared in a manner that iscompliant with laws of different jurisdictions.

As shown in FIG. 1C, and by reference number 112, the ledger managementplatform may provide the one or more smart contracts to the network ofnodes. In some implementations, the ledger management platform mayprovide the one or more smart contracts to each node in the network ofnodes.

In some implementations, the ledger management platform may provide theone or more smart contracts to one or more sets of nodes. For example,the ledger management platform may provide the one or more smartcontracts to one or more sets of nodes based on a distribution rule. Asan example, a distribution rule may indicate to provide each node with asmart contract that is in compliance with laws of a jurisdiction inwhich an organization using the node operates. As shown as an example,the first smart contract (e.g., smart contract A) may be provided to afirst set of nodes and the second smart contract (e.g., smart contractB) may be provided to a second set of nodes.

In some implementations, such as when the distributed ledger issupported by a blockchain, the network of nodes may adhere to a protocolfor inter-node communication and/or validation of new transactions. Forexample, if a first node adds a transaction to the blockchain, theprotocol may require that all other nodes in the network perform anindependent validation of the transaction. However, if a smart contractused for the transaction is not supported by every node in the network,some of the nodes in the network may be unable to independently validatenew transactions. To address this, the network of nodes may be separatedinto one or more sets of nodes, and the protocol for inter-nodecommunication and/or validation may be revised such that only nodeswithin a particular set of nodes need to comply with the protocol.

In some implementations, the ledger management platform may provide, toeach node in the network nodes, a smart contract that includes separatefunctions that comply with data privacy laws of particularjurisdictions. In this case, each node in the network of nodes maysupport the same smart contract, thereby ensuring that each node is ableto satisfy the protocol for inter-node communication and/or validationof new transactions.

In this way, the ledger management platform is able to distribute theone or more smart contacts among the nodes network.

As shown in FIG. 1D, and by reference number 114, an individual maycomplete an application for credit. For example, an individual mayinteract with an interface of a device associated with the firstorganization (shown as Device of Organization 1) to complete anapplication to apply for a particular type of credit with the firstorganization.

The individual may be applying for credit in a first country in whichthe individual does not have a credit score (e.g., a country to whichthe individual has recently moved). The individual may have a creditscore or information that may be used to determine a credit score basedon transactions performed in a second country (e.g., a country in whichthe individual has previously lived, a country in which the individualhas previously been approved for credit, etc.).

The application may be an application for a credit card, for a line ofcredit, for a home loan, and/or for any other type of credit offered bythe first organization. The application may require the individual toprovide a name, an address, contact information, a country ofcitizenship, a list of one or more credit lending institutions that hadpreviously issued credit to the individual, a list of organizations thathave rated the individual based on performance of a particular task(e.g., a ride sharing service where the individual is rated by drivers,an online shopping portal where the individual is rated by other users,etc.), and/or the like.

Furthermore, the individual may sign the application with a digitalsignature. The digital signature may be used as an indicator that theindividual has been made aware of, and/or consents to, the firstorganization requesting credit worthiness information of the individualfrom one or more organizations that are a part of the network that hasaccess to the distributed ledger (e.g., organizations that may havecredit worthiness information of the individual based on transactionsperformed in the second country).

In some cases, the individual may include the individual's blockchainidentifier in the application. For example, the distributed ledger maysupport a blockchain for the individual that provides a complete recordof all transactions where the network of nodes were used to exchangeinformation relating to the individual. In this case, the blockchainidentifier for the individual may be used by devices in the network toidentify the individual's blockchain.

Additionally, the blockchain identifier may have been assigned to theindividual when the individual registered for one or more services inthe second country (e.g., the country in which the individual has acredit score and used to live). As an example, when the individualregistered for an account with a bank in the second country, if the bankhad already joined the network to access the distributed ledger, thebank would assign the individual a blockchain identifier. In othercases, an organization (e.g., the bank) may assign the individual with ablockchain identifier after the individual has already used theorganization for one or more services.

As shown by reference number 116, the device associated with the firstorganization may provide the application to the first node (e.g., thenode associated with the first organization). As shown by referencenumber 118, the first node may select application questions that are tobe used in the application. For example, the first node may identifyapplication questions from a particular smart contract that is incompliance with data privacy laws of the first country and/or the secondcountry, and may select the identified application questions for use aspart of the individual's application. In some cases, the selectedapplication questions may be shown to the individual to comply with dataprivacy laws of a particular jurisdiction.

As shown by reference number 120, the first node may use the digitalsignature of the individual to encrypt the application. For example, theuser device of the first organization may execute a one-way hashfunction, or a similar function, to hash the application. In this case,the user device of the first organization may use the digital signatureof the individual (e.g., which effectively serves as a private key) toencrypt the hashed application. By encrypting the hashed application,the user device of the first organization conserves processing resourcesrelative to encrypting the entire application.

In some cases, a public key that is able to decrypt the hashedapplication may have been previously provisioned to one or moreorganizations that have credit worthiness information of the individual.In other cases, a public key that is able to decrypt the hashedapplication may be provided via a secure medium to one or moreorganizations that have credit worthiness information of the individual.

As shown by reference number 122, the first node may provide the ledgermanagement platform with a request for a credit worthiness score of theindividual. For example, the first node may provide the ledgermanagement platform with a request for a credit worthiness score thatincludes the encrypted application of the individual.

In this way, the individual is able to complete an application forcredit with the first organization, and the first organization is ableto use the first node to provide the ledger management platform with arequest for a credit worthiness score of the individual.

As shown in FIG. 1E, and by reference number 124, the ledger managementplatform may select one or more nodes as targets for a broadcast thatincludes the application questions. For example, the ledger managementplatform may selectively identify one or more nodes as targets for abroadcast that includes the application questions based on a broadcastrule. In this case, the ledger management platform may be configuredwith a particular broadcast rule, such as a first broadcast ruleindicating to select the one or more nodes based on informationidentified in the request for the credit worthiness score, a secondbroadcast rule indicating to select all of the nodes in the network ofnodes, a third broadcast rule indicating to select the one or more nodesbased on the one or more nodes supporting a smart contract that iscompliant with data privacy laws of a jurisdiction associated with thesecond country, and/or the like.

As an example, the ledger management platform may selectively identifyone or more nodes based on the first broadcast rule. In this case, theledger management platform may use a public key to decrypt theapplication to identify information that may be used to select one ormore nodes for the broadcast. For example, the application may include afield with a blockchain identifier of the individual, a field with acountry identifier for a country in which the individual has a creditscore or has performed transactions that may be used to determine acredit score, a field identifying a particular type of credit that theindividual had in the second country, a field identifying a particularorganization that provided credit to the individual in the secondcountry, and/or the like.

Continuing with the example, the ledger management platform may use theidentified information to select one or more nodes for the broadcast.For example, if the application includes the blockchain identifier ofthe individual, the ledger management platform may use the blockchainidentifier of the individual to search a data structure that associatesthe blockchain identifier of the individual with particularorganizations or nodes (e.g., organizations that have credit worthinessinformation of the individual may already have the blockchain identifierof the individual). As another example, if the application includes acountry identifier for a country in which the individual has a creditscore, the ledger management platform may use the country identifier tosearch a data structure that associates the country identifier withparticular organizations or nodes that operate in the second country.

As another example, the ledger management platform may identify all ofthe nodes as targets for the broadcast based on the second broadcastrule. For example, the ledger management platform may be configured withthe second broadcast rule indicating to broadcast the applicationquestions to all nodes, which may cause the ledger management platformto select all of the nodes as targets for the broadcast.

As another example, the ledger management platform may selectivelyidentify one or more nodes that support a smart contract that iscompliant with data privacy laws of a country in which the individualhas a credit score or has performed transactions that may be used todetermine a credit score. In this case, the ledger management platformmay use a public key to decrypt the application to identify a countryidentifier for a country in which the individual has a credit score orhas performed the transactions that may be used to determine the creditscore. Additionally, the ledger management platform may use the countryidentifier to reference a data structure that associates the countryidentifier with the smart contract that is in compliance with the dataprivacy laws of the second country. As such, the ledger managementplatform is able to identify one or more nodes with the countryidentifier, and may select the one or more nodes as targets for thebroadcast.

As shown by reference number 126, the ledger management platform maybroadcast the encrypted application questions to the selected nodes. Forexample, the ledger management platform may broadcast the encryptedapplication questions using an API or a similar type of interface. Insome cases, such as when the ledger management platform has to decryptthe application to access information in the application that is neededto select particular nodes for the broadcast, the ledger managementplatform may create a copy of the encrypted application, may decrypt thecopy of the encrypted application (e.g., to identify information neededto select particular nodes), and may broadcast the encrypted applicationto the selected nodes.

In other cases, the ledger management platform may only decrypt certaininformation within the application, and may leave the applicationquestions encrypted. For example, the ledger management platform maydecrypt a blockchain identifier of the individual or a countryidentifier associated with the individual, and may leave the applicationquestions encrypted. This may allow the ledger management platform touse the blockchain identifier or the country identifier to selectparticular nodes as targets for the broadcast, without having to decryptthe application questions (e.g., which need to remain encrypted whenbroadcast to the selected nodes).

As shown by reference number 128, the one or more nodes that receive thebroadcast may decrypt the application questions and generate one or moreapplication responses. For example, the one or more nodes may decryptthe application questions using a public key that has been securelyprovisioned to each node, as described elsewhere herein. By decryptingthe application questions, the application questions may be viewed on aninterface associated with each node, such that employees of eachorganization may provide application responses based on the type ofinformation that each organization has about the individual.

As shown as an example, a second organization may have access to acredit score of the individual in the second country, and may providethe credit score as an application response to the application questionthat asks for the individual's credit score. Additionally, a thirdorganization may have access to the individual's income, and may providethe income as an application response to the application question thatasks for the individual's income. Additional organizations may respondto the broadcast by providing other credit information and/or ratinginformation, such as an amount of outstanding debt, a mortgage paymenthistory, a ride sharing rating with a popular ride sharing service,and/or the like.

In some implementations, a node may automatically generate anapplication response. For example, a data source of the secondorganization may store credit information for the individual, and thenode may use the blockchain identifier of the individual or personaldata of the individual to search the data source to identify the creditinformation of the individual. In this case, the node may use a naturallanguage processing technique to parse through the application questionsand/or the stored credit information to identify information that may beused as responses for the application questions. As such, the node mayselect the information as information to include in the applicationresponse.

In this way, the ledger management platform is able to broadcast theencrypted application questions to the one or more nodes to permit theone or more nodes to generate application responses.

As shown in FIG. 1F, and by reference number 130, the one or more nodesthat generated application responses may determine whether one or moreconditions of the smart contract are satisfied. For example, a node thatgenerated an application response (e.g., the second node, the thirdnode, etc.) may provide an application response as input to the smartcontract to cause the smart contract to output an indication of whetherone or more conditions have been satisfied. As described above, the oneor more conditions of the smart contract may be conditions that, ifsatisfied, cause the ledger management platform to orchestrate providingpayment to the organization (e.g., payment for providing the firstorganization with the credit worthiness information of the individual).Additionally, satisfying one or more conditions of the smart contractmay allow a particular node to store, in the distributed ledger, arecord of the particular node satisfying one or more of the conditionsof the smart contract, as described further herein.

As shown by reference number 132, each node may encrypt an applicationresponse that has been generated. For example, the one or more nodes mayencrypt the application response using one or more techniques describedelsewhere herein. As shown by reference number 134, each node mayprovide the encrypted application responses to the ledger managementplatform.

As shown by reference number 136, the ledger management platform maydecrypt the application responses, using a technique described elsewhereherein, and may process the application responses to determine a creditworthiness score of the individual. For example, the applicationresponses may include credit information and/or rating informationrelating to the individual, and the ledger management platform maydetermine the credit worthiness score as a function of the creditinformation and/or the rating information. As an example, theapplication responses might identify the individual's credit score,income, mortgage payment history, ride sharing score, and/or the like,and the ledger management platform may apply a credit scoring algorithmthat is able to determine the credit worthiness score (e.g., byassigning weights to particular types of application responses, anddetermining a weighted average).

As shown by reference number 138, the ledger management platform mayprovide the credit worthiness score to the first node. As shown byreference number 140, the first node may determine whether to accept orreject the application based on the credit worthiness score. Forexample, the first node may accept applications with a credit worthinessscore above a particular scoring threshold. Additionally, oralternatively, the first node may use the credit worthiness score todetermine an amount of credit to offer the individual after approvingthe application. In some cases, rather than request a credit worthinessscore, the first organization may use the first node to request all ofthe credit worthiness information of the individual, and may use aninternal credit scoring algorithm to determine whether to accept theindividual's application for credit.

In this way, the ledger management platform is able to determine acredit worthiness score that is able to be used by the first node todetermine whether to accept or reject the individual's application forcredit.

As shown in FIGS. 1G and 1H, each request for information or response toa request for information may be stored as a transaction in thedistributed ledger. For example, the distributed ledger may be supportedusing one or more blockchain data structures, whereby each blockchainprovides a complete record of all transactions associated with aparticular individual.

As shown in FIG. 1G, and by reference number 142, the second node maygenerate a record of an application response provided by the secondorganization. For example, the second node may be configured to generatea record of an application response if one or more conditions of thesmart contract are satisfied.

The record may indicate the application responses that were provided,which conditions of the smart contract were satisfied by the applicationresponses, a transaction identifier to identify the transaction withinthe blockchain, personal information of the individual (e.g., metadataindicating application responses, metadata summarizing applicationresponses, etc.), and/or the like.

In some cases, the record may not include personal information of theindividual. For example, some data privacy laws require that personalinformation of an individual be stored in a manner that allows thepersonal information to be purged upon request of the individual.However, the immutable nature of the blockchain may make removal of thepersonal information of the individual difficult. As such, informationincluded in a record may omit personal information of the individual,such that a request for removal of the personal information would not beneeded.

As shown by reference number 144, the second node may store the recordof the application response as a transaction in a blockchain associatedwith the individual. For example, the second node may look up theblockchain of the individual using the blockchain identifier of theindividual that was provided as part of the broadcast to the secondnode. In this case, the second node may store the record as atransaction in the blockchain. As shown, the blockchain associated withthe individual may already include a first block that is a record of theapplication questions that were broadcast to one or more nodes in thenetwork. As such, the application response may be stored as a secondblock in the blockchain of the individual.

In some cases, as shown, each record or transaction may be stored in theblockchain as a separate block. In other cases, different data storagelogic may be used, such that a block is used to store multiple recordsor transactions.

As shown by reference number 146, the second node may secure theblockchain that includes the record of the transaction. For example, thesecond node may, after adding the record to the blockchain, generate acryptographic hash of the blockchain. In this case, each block in theblockchain may include the cryptographic hash of the prior block, suchthat the two blocks are linked. Additionally, the cryptographic hash maybe stored using a data structure, such as a Merkle tree, which may storehashed data in a manner that allows other nodes in the network to verifythe hashed data.

As shown by reference number 148, the second node may provide thesecured blockchain that includes the added transaction to the othernodes in the network. In some implementations, the second node mayprovide the secured blockchain to the ledger management platform, whichmay distribute the secured blockchain to the other nodes in the network.In some cases, such as when different sets of nodes are utilizingdifferent smart contracts, the second node may provide the securedblockchain to nodes that use the same smart contract.

As shown by reference number 150, the other nodes in the network (e.g.,all nodes except the second node, all nodes in a particular set of nodesexcept the second node, etc.) may verify the transaction that has beenadded to the blockchain. For example, the other nodes may performanother cryptographic hash of the secured blockchain that allows theother nodes to verify the transaction that has been added to theblockchain.

As shown in FIG. 1H, the third node may update the distributed ledger ina manner similar to that described with respect to the second node. Forexample, and as shown by reference number 152, the third node maygenerate a record of an application response provided by the thirdorganization. As shown by reference number 154, the third node may storethe record of the application response as a new transaction in theblockchain associated with the individual.

As shown by reference number 156, the third node may secure theblockchain associated with the individual. As shown by reference number158, the third node may provide the secured blockchain to the othernodes in the network. As shown by reference number 160, the other nodesin the network may verify the transaction.

In this way, the one or more nodes are able to update the distributedledger such that the distributed ledger includes a secure blockchaindescribing all transactions relating to the individual.

As shown in FIG. 1I, and by reference number 162, the second node andthe third node may provide, to a fourth node (e.g., a virtual walletassociated with the first organization), data indicating that one ormore conditions of the smart contract have been satisfied. For example,the second node and the third node may be configured with a smartcontract that is to provide cryptocurrency as payment if one or moreconditions are satisfied. As such, the second node and third node mayprovide the fourth node with proof that one or more conditions of thesmart contract have been satisfied.

As shown by reference number 164, the fourth node may providecryptocurrency as payment to a fifth node and a sixth node that areassociated with virtual wallets of the second organization and the thirdorganization. Payment may be made using cryptocurrency or a similar formof payment.

In this way, organizations are able to be compensated for responding torequests for information that are broadcast throughout the network.

As shown in FIG. 1J, the ledger management platform may orchestrateremoval of personal information of the individual from the distributedledger. For example, assume that the blockchain of the individualincluded personal information, and that data privacy laws allow theindividual to request removal of the personal information.

As shown by reference number 166, the ledger management may receive,from a user device associated with the individual, a request to removepersonal information of the individual. The request may include thedigital signature of the individual and the blockchain identifier of theindividual.

As shown by reference number 168, the ledger management platform mayremove personal information from one or more blocks of the blockchain ofthe individual. For example, personal information of the individual maybe stored within block metadata that describes each transaction storedby the blockchain. To obtain authorization to remove the personalinformation from the blockchain, the ledger management platform may usethe digital signature and the blockchain identifier of the individual.In some implementations, removal of the personal information may requirethe blockchain to be a permissions-based blockchain.

As shown by reference number 170, the ledger management platform maysecure the blockchain after modifying transactions to no longer includethe personal information of the individual. For example, the ledgermanagement platform may use a specialized cryptographic hash functionthat, with the private key of the individual, is able to generate one ormore cryptographic hashes of one or more blocks of the blockchain. Insome cases, the specialized cryptographic hash function may be able tocreate hash collisions, such that a transaction that includes personalinformation of the individual and a modified transaction that excludesthe personal information would produce an identical hashed value. Thismay allow an otherwise immutable blockchain to be modified in specialcircumstances such as where a law may require that an individual'spersonal information be removed.

In some cases, each block that includes removed personal information maystore metadata describing the removal. For example, a transaction thathad personal information removed may include metadata describing a timeat which the information was removed, the authorization of theindividual who requested the removal, a summary of the type ofinformation that was removed, and/or the like.

As shown by reference number 172, the ledger management platform mayprovide the secure blockchain of the individual to the other nodes inthe network. In this case, the other nodes in the network may performone or more additional actions to verify the validity of the blockchain(e.g., such as by using the specialized cryptographic hash function toperform an independent validation of the blockchain).

In this way, the ledger management platform is able to orchestrateremoval of personal information from the distributed ledger.

As indicated above, FIGS. 1A-1J are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 1A-1J. For example, there may be additional devices and/ornetworks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIGS. 1A-1J. Furthermore, two or more devices shown in FIGS.1A-1J may be implemented within a single device, or a single deviceshown in FIGS. 1A-1J may be implemented as multiple, distributeddevices. Additionally, or alternatively, a set of devices (e.g., one ormore devices) of example implementations 100 may perform one or morefunctions described as being performed by another set of devices ofexample implementations 100.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG. 2, environment 200 may include a user device 210, one or more nodes 220,a ledger management platform 230 supported by a cloud computingenvironment 240, a data source 250, and/or a network 260. Devices ofenvironment 200 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

User device 210 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith an application for credit. For example, user device 210 may includea communication and/or computing device, such as a mobile phone (e.g., asmart phone, a radiotelephone, etc.), a laptop computer, a tabletcomputer, a handheld computer, a server computer, a gaming device, awearable communication device (e.g., a smart wristwatch, a pair of smarteyeglasses, etc.), or a similar type of device. In some implementations,user device 210 may provide, to ledger management platform 230, arequest to remove personal information of an individual.

Node 220 includes one or more devices capable of receiving, generating,storing, processing, and/or providing information associated with creditworthiness information of an individual. For example, node 220 mayinclude a communication and/or computing device, such as a serverdevice, a desktop computer, a laptop computer, a tablet computer, ahandheld computer, a mobile phone (e.g., a smart phone, aradiotelephone, etc.), or a similar type of device.

In some implementations, node 220 may be a node in a network that hasaccess to a distributed ledger that is supported by a blockchain. Insome implementations, node 220 may be installed on a device associatedwith an organization that wants to use the distributed ledger forsharing credit worthiness information of individuals. In someimplementations, node 220 may be a server that is not local to anorganization that wants to use the distributed ledger (e.g., a server ina data center), and may be assigned to the organization that wants touse the distributed ledger. In this case, an employee of theorganization may interact with an interface of a device associated withthe organization to access one or more services provided by node 220.

In some implementations, node 220 may be used to generate an applicationfor credit. In some implementations, node 220 may receive an applicationfor credit from a device associated with an organization that has accessto the distributed ledger. In some implementations, node 220 may provideledger management platform 230 with a request for a credit worthinessscore of an individual. In some implementations, node 220 may provideencrypted application responses to ledger management platform 230.

In some implementations, node 220 may be part of a network of nodes 220that are not managed by a management node. In some implementations, node220 may be part of a network of nodes 220 that are managed by ledgermanagement platform 230.

Ledger management platform 230 includes one or more devices capable ofreceiving, generating, storing, processing, and/or providing informationassociated with credit worthiness information of an individual. Forexample, ledger management platform 230 may include a server device(e.g., a host server, a web server, an application server, etc.), a datacenter device, or a similar device. In some implementations, ledgermanagement platform 230 may be part of a network of nodes 220 that haveaccess to a distributed ledger that is supported by a blockchain.

In some implementations, ledger management platform 230 may interactwith one or more devices associated with organizations to sign theorganizations up for access to the distributed ledger. In someimplementations, ledger management platform 230 may provide instructionson how to access the distributed ledger to the one or more devicesassociated with the organizations.

In some implementations, ledger management platform 230 may interactwith one or more nodes 220 to orchestrate distribution of creditworthiness information of an individual. In some implementations, ledgermanagement platform 230 may receive requests for a credit worthinessscore for an individual. In some implementations, ledger managementplatform 230 may broadcast, to one or more nodes 220, applicationquestions for an individual's application for credit. In someimplementations, ledger management platform 230 may receive applicationresponses from one or more nodes 220.

In some implementations, ledger management platform 230 may providesmart contracts to devices associated with validation entities, and mayreceive validated smart contracts from the devices associated withvalidation entities. In some implementations, ledger management platform230 may provide smart contracts to nodes 220.

In some implementations, ledger management platform 230 may provide acredit worthiness score of an individual to node 220. In someimplementations, ledger management platform 230 may provide the secureblockchain of an individual to node 220 (e.g., a blockchain that hasbeen hashed with a new transaction).

In some implementations, as shown, ledger management platform 230 may behosted in cloud computing environment 240. Notably, whileimplementations described herein describe ledger management platform 230as being hosted in cloud computing environment 240, in someimplementations, ledger management platform 230 might not be cloud-based(i.e., may be implemented outside of a cloud computing environment) ormight be partially cloud-based.

Cloud computing environment 240 includes an environment that deliverscomputing as a service, whereby shared resources, services, etc. may beprovided to user device 210, node 220, data source 250, and/or ledgermanagement platform 230. Cloud computing environment 240 may providecomputation, software, data access, storage, and/or other services thatdo not require end-user knowledge of a physical location andconfiguration of a system and/or a device that delivers the services. Asshown, cloud computing environment 240 may include a ledger managementplatform 230 and one or more computing resources 235.

Computing resource 235 includes one or more personal computers,workstation computers, server devices, or another type of computationand/or communication device. In some implementations, computing resource235 may host ledger management platform 230. The cloud resources mayinclude compute instances executing in computing resource 235, storagedevices provided in computing resource 235, data transfer devicesprovided by computing resource 235, and/or the like. In someimplementations, computing resource 235 may communicate with othercomputing resources 235 via wired connections, wireless connections, ora combination of wired and wireless connections. In someimplementations, computing resource 235 may perform one or morefunctions or implementations described as being performed by node 220.

As further shown in FIG. 2 , computing resource 235 may include a groupof cloud resources, such as one or more applications (“APPs”) 235-1, oneor more virtual machines (“VMs”) 235-2, virtualized storage (“VSs”)235-3, one or more hypervisors (“HYPs”) 235-4, or the like.

Application 235-1 includes one or more software applications that may beprovided to or accessed by user device 210. Application 235-1 mayeliminate a need to install and execute the software applications onuser device 210. For example, application 235-1 may include softwareassociated with ledger management platform 230 and/or any other softwarecapable of being provided via cloud computing environment 240. In someimplementations, one application 235-1 may send/receive informationto/from one or more other applications 235-1, via virtual machine 235-2.

Virtual machine 235-2 includes a software implementation of a machine(e.g., a computer) that executes programs like a physical machine.Virtual machine 235-2 may be either a system virtual machine or aprocess virtual machine, depending upon use and degree of correspondenceto any real machine by virtual machine 235-2. A system virtual machinemay provide a complete system platform that supports execution of acomplete operating system (“OS”). A process virtual machine may executea single program, and may support a single process. In someimplementations, virtual machine 235-2 may execute on behalf of a user(e.g., user device 210), and may manage infrastructure of cloudcomputing environment 240, such as data management, synchronization, orlong-duration data transfers.

Virtualized storage 235-3 includes one or more storage systems and/orone or more devices that use virtualization techniques within thestorage systems or devices of computing resource 235. In someimplementations, within the context of a storage system, types ofvirtualizations may include block virtualization and filevirtualization. Block virtualization may refer to abstraction (orseparation) of logical storage from physical storage so that the storagesystem may be accessed without regard to physical storage orheterogeneous structure. The separation may permit administrators of thestorage system flexibility in how the administrators manage storage forend users. File virtualization may eliminate dependencies between dataaccessed at a file level and a location where files are physicallystored. This may enable optimization of storage use, serverconsolidation, and/or performance of non-disruptive file migrations.

Hypervisor 235-4 provides hardware virtualization techniques that allowmultiple operating systems (e.g., “guest operating systems”) to executeconcurrently on a host computer, such as computing resource 235.Hypervisor 235-4 may present a virtual operating platform to the guestoperating systems, and may manage the execution of the guest operatingsystems. Multiple instances of a variety of operating systems may sharevirtualized hardware resources.

Data source 250 includes one or more devices capable of receiving,storing, generating, processing, and/or providing information associatedwith an organization. For example, data source 250 may include a serverdevice or a group of server devices. In some implementations, datasource 250 may store credit worthiness information associated with anindividual.

Network 260 includes one or more wired and/or wireless networks. Forexample, network 260 may include a cellular network (e.g., a fifthgeneration (5G) network, a fourth generation (4G) network, such as along-term evolution (LTE) network, a third generation (3G) network, acode division multiple access (CDMA) network, a public land mobilenetwork (PLMN), a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), a telephone network (e.g., the PublicSwitched Telephone Network (PSTN)), a private network, an ad hocnetwork, an intranet, the Internet, a fiber optic-based network, a cloudcomputing network, or the like, and/or a combination of these or othertypes of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2 . Furthermore, two or more devices shown in FIG. 2 maybe implemented within a single device, or a single device shown in FIG.2 may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to user device 210, node 220, ledger management platform230, computing resource 235, and/or data source 250. In someimplementations, user device 210, node 220, ledger management platform230, computing resource 235, and/or data source 250 may include one ormore devices 300 and/or one or more components of device 300. As shownin FIG. 3 , device 300 may include a bus 310, a processor 320, a memory330, a storage component 340, an input component 350, an outputcomponent 360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3 . Additionally, or alternatively,a set of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for using a securedistributed ledger to manage sharing of credit worthiness information ofindividuals. In some implementations, one or more process blocks of FIG.4 may be performed by a ledger management platform (e.g., ledgermanagement platform 230). In some implementations, one or more processblocks of FIG. 4 may be performed by another device or a group ofdevices separate from or including the ledger management platform, suchas a user device (e.g., user device 210), one or more nodes (e.g., oneor more nodes 220), and/or a data source (e.g., data source 250).

As shown in FIG. 4 , process 400 may include receiving, from a firstdevice, a request for a credit worthiness score for an individual thatis applying for credit (block 410). For example, the ledger managementplatform (e.g., using processor 320, memory 330, input component 350,communication interface 370, etc.) may receive, from a first device(e.g., a first node of the one or more nodes), a request for a creditworthiness score for an individual that is applying for credit, asdescribed above in connection with FIGS. 1A-1J.

In some implementations, the first device may be associated with anorganization offering the credit. In some implementations, the requestmay include application questions that have been encrypted using aprivate key associated with a digital signature of the individual. Insome implementations, the first device may be part of a network ofdevices that have access to a distributed ledger for sharing creditworthiness information of a group of individuals.

As further shown in FIG. 4 , process 400 may include broadcasting theapplication questions that have been encrypted to one or more additionaldevices to cause at least one of the one or more additional devices togenerate an application response that includes responses to theapplication questions, record the application response in thedistributed ledger, and provide the application response to the device(block 420). For example, the ledger management platform (e.g., usingprocessor 320, output component 360, communication interface 370, etc.)may broadcast the application questions that have been encrypted to oneor more additional devices (e.g., one or more nodes) to cause at leastone of the one or more additional devices to generate an applicationresponse that includes responses to the application questions, recordthe application response in the distributed ledger, and provide theapplication response to the ledger management platform, as describedabove in connection with FIGS. 1A-1J. In some implementations, the oneor more additional devices may be part of the network of devices thathave access to the distributed ledger.

As further shown in FIG. 4 , process 400 may include receiving, from atleast one of the one or more additional devices, one or more applicationresponses that have been encrypted (block 430). For example, the ledgermanagement platform (e.g., using processor 320, input component 350,communication interface 370, etc.) may receive, from at least one of theone or more additional devices, one or more application responses thathave been encrypted, as described above in connection with FIGS. 1A-1J.In some implementations, each application response, of the one or moreapplication responses, may include particular credit worthinessinformation relating to the individual.

As further shown in FIG. 4 , process 400 may include decrypting the oneor more application responses (block 440). For example, the ledgermanagement platform (e.g., using processor 320, etc.) may decrypt theone or more application responses, as described above in connection withFIGS. 1A-1J.

As further shown in FIG. 4 , process 400 may include determining thecredit worthiness score using the one or more application responses thathave been decrypted (block 450). For example, the ledger managementplatform (e.g., using processor 320, etc.) may determine the creditworthiness score using the one or more application responses that havebeen decrypted, as described above in connection with FIGS. 1A-1J.

As further shown in FIG. 4 , process 400 may include providing thecredit worthiness score to the first device to allow the first device touse the credit worthiness score to determine whether to approve theindividual for the credit (block 460). For example, the ledgermanagement platform (e.g., using processor 320, output component 360,communication interface 370, etc.) may provide the credit worthinessscore to the first device to allow the first device to use the creditworthiness score to determine whether to approve the individual for thecredit, as described above in connection with FIGS. 1A-1J.

Process 400 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In some implementations, the individual may apply for the credit in afirst country and the particular credit worthiness information mayrelate to transactions performed by the individual in a second country.

In some implementations, the ledger management platform may receive,from a first group of additional devices of the one or more additionaldevices, credit information for the individual. Additionally, the ledgermanagement platform may receive, from a second group of additionaldevices of the one or more additional devices, rating information thatincludes one or more ratings associated with the individual based onhistorical transactions with one or more particular organizations. Insome implementations, the ledger management platform may determine thecredit worthiness score as a function of the credit information and therating information.

In some implementations, the ledger management platform may selectivelyidentify, before broadcasting the application questions, the one or moreadditional devices as targets for the broadcast, based on a broadcastrule. In some implementations, the broadcast rule may be a firstbroadcast rule to select the one or more additional devices based oninformation identified in the request for the credit worthiness score, asecond broadcast rule to select the one or more additional devices basedon the one or more additional devices having access to the distributedledger, a third broadcast rule to select the one or more additionaldevices based on the one or more additional devices supporting a smartcontract that is compliant with data privacy laws of a country in whichthe individual has previously performed transactions, and/or the like.

In some implementations, the ledger management platform may validate,before receiving the request for the credit worthiness score, a smartcontract that is to be used to provide cryptocurrency in exchange forthe particular credit worthiness information of the individual. In someimplementations, the ledger management platform may validate the smartcontract using a machine learning model that is trained on informationindicating data privacy laws of a plurality of jurisdictions associatedwith the group of individuals and historical smart contracts. In someimplementations, the ledger management platform may validate the smartcontact using a validation technique performed by a particular group ofdevices associated with one or more validation entities. In someimplementations, the ledger management platform may provide the smartcontract to the first device and to the one or more additional devices.

In some implementations, the ledger management platform may provide,before receiving the request and to the one or more additional devices,a smart contract that includes executable instructions capable ofverifying whether the particular credit worthiness information is incompliance with data privacy laws of a particular jurisdiction. In someimplementations, when broadcasting the application questions, the ledgermanagement platform may broadcast the application questions to the oneor more additional devices to cause at least one of the one or moreadditional devices to generate the application response that includesthe particular credit worthiness information relating to the individual,and provide the application response as input to the smart contract tocause the smart contract to verify that the particular credit worthinessinformation complies with the data privacy laws of the particularjurisdiction.

In some implementations, the distributed ledger may be supported by ablockchain, and the ledger management platform may receive, from theuser device associated with the individual, a particular request toremove the particular credit worthiness information of the individualfrom the distributed ledger. In some implementations, the particularrequest may include the private key and a blockchain identifier for theindividual. In some implementations, the ledger management platform mayidentify the particular credit worthiness information of the individualusing the blockchain identifier. In some implementations, the ledgermanagement platform may perform one or more actions associated withusing the private key to remove the particular credit worthinessinformation from the distributed ledger. In some implementations,removal of the particular credit worthiness information may be able tobe cryptographically proven.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4 . Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5 is a flow chart of an example process 500 for using a securedistributed ledger to manage sharing of credit worthiness information ofindividuals. In some implementations, one or more process blocks of FIG.5 may be performed by a ledger management platform (e.g., ledgermanagement platform 230). In some implementations, one or more processblocks of FIG. 5 may be performed by another device or a group ofdevices separate from or including the ledger management platform, suchas a user device (e.g., user device 210), one or more nodes (e.g., oneor more nodes 220), and/or a data source (e.g., data source 250).

As shown in FIG. 5 , process 500 may include receiving applicationquestions for an individual that is applying for credit with a firstorganization (block 510). For example, the ledger management platform(e.g., using processor 320, memory 330, input component 350,communication interface 370, etc.) may receive application questions foran individual that is applying for credit with a first organization, asdescribed above in connection with FIGS. 1A-1J. In some implementations,the ledger management platform may be part of a network of devices thathave access to a distributed ledger for sharing credit worthinessinformation for a group of individuals. In some implementations, theapplication questions may have been encrypted using a private keyassociated with the individual.

As further shown in FIG. 5 , process 500 may include broadcasting theapplication questions to one or more additional devices, that haveaccess to the distributed ledger, to cause at least one of the one ormore additional devices to generate an application response thatincludes responses to the application questions, process the applicationresponse using a smart contract, and provide the application response tothe device (block 520). For example, the ledger management platform(e.g., using processor 320, output component 360, communicationinterface 370, etc.) may broadcast the application questions to one ormore additional devices (e.g., one or more of the nodes), that haveaccess to the distributed ledger, to cause at least one of the one ormore additional devices to generate an application response thatincludes responses to the application questions, process the applicationresponse using a smart contract, and provide the application response tothe device, as described above in connection with FIGS. 1A-1J.

As further shown in FIG. 5 , process 500 may include receiving, from atleast one of the one or more additional devices, one or more applicationresponses that have been encrypted (block 530). For example, the ledgermanagement platform (e.g., using processor 320, input component 350,communication interface 370, etc.) may receive, from at least one of theone or more additional devices, one or more application responses thathave been encrypted, as described above in connection with FIGS. 1A-1J.In some implementations, each application response, of the one or moreapplication responses, may include particular credit worthinessinformation relating to the individual.

As further shown in FIG. 5 , process 500 may include decrypting the oneor more application responses (block 540). For example, the ledgermanagement platform (e.g., using processor 320, etc.) may decrypt theone or more application responses, as described above in connection withFIGS. 1A-1J.

As shown in FIG. 5 , process 500 may include determining a creditworthiness score for the individual using the one or more applicationresponses (block 550). For example, the ledger management platform(e.g., using processor 320, etc.) may determine a credit worthinessscore for the individual using the one or more application responses, asdescribed above in connection with FIGS. 1A-1J.

As further shown in FIG. 5 , process 500 may include performing one ormore actions that allow the device or another device associated with thefirst organization to use the credit worthiness score to determinewhether to approve the individual for credit (block 560). For example,the ledger management platform (e.g., using processor 320, inputcomponent 350, output component 360, communication interface 370, etc.)may perform one or more actions that allow the device or another deviceassociated with the first organization to use the credit worthinessscore to determine whether to approve the individual for credit, asdescribed above in connection with FIGS. 1A-1J.

Process 500 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In some implementations, the particular credit worthiness informationmay include credit information for the individual or rating informationindicating a rating associated with the individual based on historicaltransactions with a particular organization. In some implementations,the individual may be applying for the credit in a first country and theparticular credit worthiness information for the individual may relateto transactions performed by the individual in a second country.

In some implementations, the ledger management platform may selectivelyidentify the one or more additional devices as targets to receive theapplication questions based on a broadcast rule. In someimplementations, the broadcast rule may indicate to selectively identifyparticular devices that are associated with identifiers of organizationsthat transacted with the individual in a country in which the individualhas previously performed transactions.

In some implementations, the ledger management platform may store, afterproviding the application questions to the one or more additionaldevices, the application questions in the distributed ledger as atransaction associated with the individual. In some implementations, theledger management platform may provide data specifying the transactionto the one or more additional devices to permit the one or moreadditional devices to add the data specifying the transaction to a copyof the distributed ledger.

In some implementations, the ledger management platform may receive,from an additional device of the one or more additional devices, anindication that a particular application response satisfied one or moreconditions of the smart contract. In some implementations, theadditional device may be associated with a second organization thattransacted with the individual in a country in which the individual haspreviously performed transactions. In some implementations, the ledgermanagement platform may cause cryptographic currency to transfer from afirst account associated with the first organization to a second accountassociated with the second organization, based on receiving theindication that the particular application response satisfied the one ormore conditions of the smart contract.

In some implementations, the ledger management platform may receive,after broadcasting the application questions and from a particulardevice included in the network of devices, an indication that aparticular application response did not comply with data privacy laws ofa first country in which the individual used to reside and/or a secondcountry in which the individual is applying for the credit. In someimplementations, the ledger management platform may perform one or moreactions associated with removal of the particular application responsefrom the distributed ledger. In some implementations, the ledgermanagement platform may provide, to the particular device, one or morerecommendations on how to modify the particular application response toput the particular application response in compliance with the dataprivacy laws.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5 . Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

FIG. 6 is a flow chart of an example process 600 for using a securedistributed ledger to manage sharing of credit worthiness information ofindividuals. In some implementations, one or more process blocks of FIG.6 may be performed by a ledger management platform (e.g., ledgermanagement platform 230). In some implementations, one or more processblocks of FIG. 6 may be performed by another device or a group ofdevices separate from or including the ledger management platform, suchas a user device (e.g., user device 210), one or more nodes (e.g., oneor more nodes 220), and/or a data source (e.g., data source 250).

As shown in FIG. 6 , process 600 may include receiving a request for acredit worthiness score for an individual that is applying for credit ina first country (block 610). For example, the ledger management platform(e.g., using processor 320, input component 350, communication interface370, etc.) may receive a request for a credit worthiness score for anindividual that is applying for credit in a first country, as describedabove in connection with FIGS. 1A-1J. In some implementations, the firstdevice may be associated with an organization offering the credit. Insome implementations, the request may include application questions thathave been encrypted. In some implementations, the first device may bepart of a network of devices that have access to a distributed ledgerfor sharing credit worthiness information of a group of individuals.

As further shown in FIG. 6 , process 600 may include selecting one ormore additional devices in the network of devices as targets to receivethe application questions (block 620). For example, the ledgermanagement platform (e.g., using processor 320, etc.) may select one ormore additional devices (e.g., one or more of the nodes) in the networkof devices as targets to receive the application questions, as describedabove in connection with FIGS. 1A-1J.

As further shown in FIG. 6 , process 600 may include broadcasting theapplication questions to the one or more additional devices that havebeen selected to permit at least one of the one or more additionaldevices to generate an application response that includes responses tothe application questions and provide the application response to theone or more processors (block 630). For example, the ledger managementplatform (e.g., using processor 320, output component 360, communicationinterface 370, etc.) may broadcast the application questions to the oneor more additional devices that have been selected to permit at leastone of the one or more additional devices to generate an applicationresponse that includes responses to the application questions and toprovide the application response to one or more processors associatedwith the ledger management platform, as described above in connectionwith FIGS. 1A-1J.

As further shown in FIG. 6 , process 600 may include receiving, from atleast one of the one or more additional devices, one or more applicationresponses that have been encrypted (block 640). For example, the ledgermanagement platform (e.g., using processor 320, input component 350,communication interface 370, etc.) may receive, from at least one of theone or more additional devices, one or more application responses thathave been encrypted, as described above in connection with FIGS. 1A-1J.In some implementations, each application response, of the one or moreapplication responses, may include particular credit worthinessinformation relating to transactions performed by the individual in asecond country.

As further shown in FIG. 6 , process 600 may include decrypting the oneor more application responses (block 650). For example, the ledgermanagement platform (e.g., using processor 320, etc.) may decrypt theone or more application responses, as described above in connection withFIGS. 1A-1J.

As further shown in FIG. 6 , process 600 may include determining thecredit worthiness score using the one or more application responses thathave been decrypted (block 660). For example, the ledger managementplatform (e.g., using processor 320, etc.) may determine the creditworthiness score using the one or more application responses that havebeen decrypted, as described above in connection with FIGS. 1A-1J.

As further shown in FIG. 6 , process 600 may include providing thecredit worthiness score to the first device to allow the first device touse the credit worthiness score to determine whether to approve theindividual for the credit (block 670). For example, the ledgermanagement platform (e.g., using processor 320, memory 330, storagecomponent 340, and/or the like) may provide the credit worthiness scoreto the first device to allow the first device to use the creditworthiness score to determine whether to approve the individual for thecredit, as described above in connection with FIGS. 1A-1J.

Process 600 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In some implementations, the particular credit worthiness informationmay include credit information for the individual or rating informationindicating a rating associated with the individual based on historicaltransactions with a particular organization.

In some implementations, the ledger management platform may selectivelyidentify the one or more additional devices as targets for the broadcastbased on a broadcast rule. In some implementations, the broadcast rulemay include a first broadcast rule to select the one or more additionaldevices based on information identified in the request for the creditworthiness score, a second broadcast rule to select the one or moreadditional devices based on the one or more additional devices havingaccess to the distributed ledger, a third broadcast rule to select theone or more additional devices based on the one or more additionaldevices supporting a smart contract that is compliant with data privacylaws of the second country in which the individual has previouslyperformed transactions, and/or the like.

In some implementations, the ledger management platform may store thecredit worthiness score in the distributed ledger as a particulartransaction associated with the individual. In some implementations, oneor more blocks of a blockchain may be used to store a record oftransactions associated with the individual. In some implementations,the one or more blocks may also store a first transaction associatedwith the application questions and one or more additional transactionsassociated with the one or more application responses. In someimplementations, the ledger management platform may provide, to thefirst device and the one or more additional devices, a copy of thedistributed ledger that includes the particular transaction.

In some implementations, the ledger management platform may determinethe credit worthiness score based on a condition being satisfied. Insome implementations, the condition may be an expiration of a timer orreceipt of a threshold number of received application responses.

In some implementations, the ledger management platform may receive aparticular request to remove information relating to the individual fromthe distributed ledger. In some implementations, the particular requestmay include an identifier for the individual that is capable ofidentifying a storage location in the distributed ledger that is used tostore the information relating to the individual and a private keyassociated with the individual. In some implementations, the ledgermanagement platform may identify the information relating to theindividual using the identifier. In some implementations, the ledgermanagement platform may perform one or more actions associated withusing the private key to remove the information relating to theindividual.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6 . Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

In this way, the ledger management platform is able to provide a creditworthiness score that may be used to determine whether to approve anindividual for credit. Additionally, the ledger management platform isable to facilitate the distribution of credit worthiness information ina manner that is flexible, secure, distributed, and automated. Forexample, flexibility is provided by enabling execution of various smartcontracts to ensure that credit worthiness information is shared in amanner that is compliant with laws of different jurisdictions.

Additionally, security is provided by supporting a distributed ledgerwith a tamper-resistant data structure (e.g., a blockchain), byimplementing various forms of authentication, by restricting access tothe distributed ledger to particular parties, and/or the like. Forexample, the distributed ledger may improve security by preserving animmutable record of credit worthiness information, by usingcryptographic links between blocks of the distributed ledger (e.g.,reducing the potential for unauthorized tampering with the creditworthiness information), and/or the like. Security is further improvedas a result of devices that have access to the distributed ledgerindependently verifying each transaction that is added to thedistributed ledger. Moreover, use of a distributed ledger also providesfailover protection, in that the ledger management platform may continueto operate in a situation where one or more devices that have access tothe distributed ledger fail.

Furthermore, several different stages of the process for managing creditworthiness information are automated, which may remove humansubjectivity and waste from the process, and which may improve speed andefficiency of the process and conserve computing resources (e.g.,processor resources, memory resources, and/or the like). Additionally,implementations described herein use a rigorous, computerized process toperform tasks or roles that were not previously performed or werepreviously performed using subjective human intuition or input. Finally,automating the process for managing credit worthiness informationconserves computing resources (e.g., processor resources, memoryresources, and/or the like) that would otherwise be wasted by usingmultiple different types of devices with different software, protocols,and configurations, and computing resources that would otherwise bewasted correcting problems that would arise from lack of consistency inthe application of various transactions related to the credit worthinessinformation.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, or the like.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

To the extent embodiments and/or implementations described hereinutilize personal information (referred to in some jurisdictions aspersonally identifiable information (PII)), it should be understood thatsuch personal information is to be used in accordance with allapplicable laws concerning protection of that personal information.Furthermore, in many cases, use of the information may be subject toconsent of an individual. Moreover, storage of the information mayutilize various encryption techniques to protect the security andintegrity of the information. Additionally, some jurisdictions mayinclude laws indicating that the information is to be stored in a mannerthat allows the individual the request removal of the information, mayinclude laws indicating that particular types of information are unableto be stored, and/or the like.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a device andfrom a user device associated with an individual, a request to removeparticular credit worthiness information from a distributed ledger,wherein the request includes a private key and a blockchain identifierfor the individual; identifying, by the device and in the distributedledger, the particular credit worthiness information using theblockchain identifier; and performing, by the device, one or moreactions associated with the private key to remove the particular creditworthiness information from the distributed ledger.
 2. The method ofclaim 1, wherein identifying the particular credit worthinessinformation includes: using the blockchain identifier to search a datastructure that associates the blockchain identifier with particularnodes.
 3. The method of claim 1, wherein the request includes a digitalsignature of the individual, and wherein performing the one or moreactions includes: using the digital signature to obtain authorizationfor removing the particular credit worthiness information.
 4. The methodof claim 1, wherein the distributed ledger is associated with apermissions-based blockchain.
 5. The method of claim 1, whereinperforming the one or more actions includes: securing the distributedledger using a cryptographic hash function with the private key.
 6. Themethod of claim 1, wherein performing the one or more actions includes:storing metadata describing the removal of the particular creditworthiness information in each block of the distributed ledger.
 7. Themethod of claim 1, wherein the particular credit worthiness informationincludes information indicating one or more of: a credit score, anincome, a number of open lines of credit, an amount of outstanding debt,a mortgage payment history, a number of timely payments made, or anumber of untimely payments made.
 8. A device, comprising: one or morememories; and one or more processors, coupled to the one or morememories, configured to: receive, from a user device associated with anindividual, a request to remove particular credit worthiness informationfrom a distributed ledger, wherein the request includes a private keyand a blockchain identifier for the individual; identify, in thedistributed ledger, the particular credit worthiness information usingthe blockchain identifier; and perform one or more actions associatedwith the private key to remove the particular credit worthinessinformation from the distributed ledger.
 9. The device of claim 8,wherein the one or more processors, when identifying the particularcredit worthiness information, are configured to: use the blockchainidentifier to search a data structure that associates the blockchainidentifier with particular nodes.
 10. The device of claim 8, wherein therequest includes a digital signature of the individual, and wherein theone or more processors, when performing the one or more actions, areconfigured to: use the digital signature to obtain authorization forremoving the particular credit worthiness information.
 11. The device ofclaim 8, wherein the distributed ledger is associated with apermissions-based blockchain.
 12. The device of claim 8, wherein the oneor more processors, when performing the one or more actions, areconfigured to: secure the distributed ledger using a cryptographic hashfunction with the private key.
 13. The device of claim 8, wherein theone or more processors, when performing the one or more actions, areconfigured to: store metadata describing the removal of the particularcredit worthiness information in each block of the distributed ledger.14. The device of claim 8, wherein the particular credit worthinessinformation includes information indicating one or more of: a creditscore, an income, a number of open lines of credit, an amount ofoutstanding debt, a mortgage payment history, a number of timelypayments made, or a number of untimely payments made.
 15. Anon-transitory computer-readable medium storing a set of instructions,the set of instructions comprising: one or more instructions that, whenexecuted by one or more processors of a device, cause the device to:receive, from a user device associated with an individual, a request toremove particular credit worthiness information from a distributedledger, wherein the request includes a private key and a blockchainidentifier for the individual; identify, in the distributed ledger, theparticular credit worthiness information using the blockchainidentifier; and perform one or more actions associated with the privatekey to remove the particular credit worthiness information from thedistributed ledger.
 16. The non-transitory computer-readable medium ofclaim 15, wherein the request includes a digital signature of theindividual, and wherein the one or more instructions, that cause thedevice to perform the one or more actions, cause the device to: use thedigital signature to obtain authorization for removing the particularcredit worthiness information.
 17. The non-transitory computer-readablemedium of claim 15, wherein the distributed ledger is associated with apermissions-based blockchain.
 18. The non-transitory computer-readablemedium of claim 15, wherein the one or more instructions, that cause thedevice to perform the one or more actions, cause the device to: securethe distributed ledger using a cryptographic hash function with theprivate key.
 19. The non-transitory computer-readable medium of claim15, wherein the one or more instructions, that cause the device toperform the one or more actions, cause the device to: store metadatadescribing the removal of the particular credit worthiness informationin each block of the distributed ledger.
 20. The non-transitorycomputer-readable medium of claim 15, wherein the particular creditworthiness information includes information indicating one or more of: acredit score, an income, a number of open lines of credit, an amount ofoutstanding debt, a mortgage payment history, a number of timelypayments made, or a number of untimely payments made.